home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
b2day321.zip
/
BBS2DAY.DOC
< prev
next >
Wrap
Text File
|
1991-07-08
|
51KB
|
1,184 lines
════════════════════════════════════════════════════
BBS2DAY
════════════════════════════════════════════════════
Version 3.20
08 July 91
The definable Mailer / BBS System-Usage-Graph Generator
for
QuickBBS / Remote Access / SuperBBS / OPUS 1.1 / Maximus
in conjunction with
D'Bridge / FrontDoor / BinkleyTerm
by
Robert Hermans
Copyright (C) 1988-1991 Robert Hermans. All rights reserved.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ WHAT IS BBS2DAY ? █▓▒░
═════════════════════════════════════════════════════════════════════════════
BBS2DAY is a professional BBS System - Usage - Graph generator, simular
in operation to the QuickBBS/RA owns System-usage-graph (menu-type 10), but
it is a lot BETTER, MORE ATTRACTIVE and can do MUCH MORE!
BBS2DAY can be used with QuickBBS, RemoteAccess, SuperBBS, OPUS and
Maximus. It combines the internal BBS system-usage details with those from
the FrontDoor, BinkleyTerm or D'Bridge (Mailers), so you and your users
can get a "real" idea of what's going on in your BBS system.
BBS2DAY features a new command - a definable usage graph. With this
command you can build detailed reports from the mailer & bbs system usage
data files by
you defined time-length. There's also a report of the weekly bbs usage.
BBS2DAY started it's way in December of 1989 as an exact clone of QBS
by ...... and it is written using Borland's TURBO Pascal 6.0.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ DISCLAIMER, LICENSE AND OTHER IMPORTANT STUFF █▓▒░
═════════════════════════════════════════════════════════════════════════════
The following points must be considered, understood and agreed upon
BEFORE you use BBS2DAY.
* BBS2DAY is ShareWare, and not FreeWare or Public Domain !
* This documentation and the accompanying program is copyrighted material
by Robert Hermans.
* Although care has been taken to write and test a program that does what
this documentation states, the program is provided as it is, without
warranty or guarantee of any kind, either expressed or implied, as to
the quality or performance of this program, except that it will occupy
disk space.
* You may not make any changes or modifications to the program and you may
not de-compile, disassemble, or otherwise reverse-engineer it. You may
not rent or lease it to others.
* The author will not be held liable to you or anyone for any direct,
indirect, incidental, consequential or other similar damages, including
any lost profits, lost savings which may result from the use or inability
to use this program. Your use of the program constitutes your agreement
to this disclaimer and your release of the author from any form of
liability or litigation.
* I grant you a limited license to use BBS2DAY and encourage you to copy
and distribute it in an unmodified way as much as you want, as long as
you still abide to the conditions mentioned here and no money or other
compensation is asked or accepted.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ INSTALLATION & CONFIGURATION For QuickBBS, RemoteAccess, SuperBBS █▓▒░
═════════════════════════════════════════════════════════════════════════════
* Put all EXE-files or at least BBS2DAY.EXE somewhere on your hard disk.
* Enter your info and wishes in the control file BBS2DAY.CTL. You won't
have much trouble with this. Make sure that BBS2DAY can find that file
in the current directory when it is started or place the drive/path and
filename of your controlfile as a command-parameter after BBS2DAY.EXE.
* Put BBS2DAY in your batch file to run it in your daily event or after
each user.
* Now you have to change the option in your menu for the system usage graph,
from menu type 10 to 45 (or 5), and too place the following on the
optional data-line: 2DAY
2DAYWEEK for the weekly report or 2DAYUSA for the definable one.
* Registered users can also show their bbs-users a system usage graph
of the FrontDoor/Binkley/D'Bridge activity. To do so you just have
to place a additional line in your menu with type 45 (or 5) and a
data-line saying: 2DAYMAIL
* BBS2DAY will create the reports in your text files path (which is
obtained from the CONFIG file). BBS2DAY will put a Ctrl-L (Screen
Clearing Codes) in the beginning of the file. You can display these
files to your users by using QuickBBS (RA/SuperBBS) TYPE 5 or TYPE 45
("Press [ENTER] to continue:" ) commands.
* BBS2DAY will create two files named 2DAY.ASC and 2DAY.ANS. A file
called BBS2DAY.DAT will be created by enabling Mailer activity. This
file stores all information needed to process a mailer activity chart.
The use of BBS2DAY with "DEFINABLE-USAGE" enabled or B2DAY-UP.EXE will
cause you to find two additional files on you harddisk: BBS2DAY!.DAT
and BBS2DAY!.DTA. These files store all neccessary data to generate
your desired definable usage report.
* BBS2DAY and/or B2DAY-UP must be started everytime a user log's off so
the system-usage-graph will be up too date. You may also run BBS2DAY
in a event if you like, but then the system-usage-graph will not be so
up too date as running BBS2DAY everytime a user logs off. Running
BBS2DAY with "DEFINABLE-USAGE" enabled in a event is possible, but
you have to run B2DAY-UP.EXE every time a user log's off to store all
needed data. B2DAY-UP and BBS2DAY get their information out of
SYSINFO.BBS and USERS.BBS.
* I suggest running BBS2DAY / B2DAY-UP after a user logs off and everytime
a mailer called if FrontDoor/Binkley/D'Bridge activity is enabled.
* Running a Multi-Line-Bulletin-Board
If your running a multi-line BBS you have to create a config-file for
each line your running containing all needed data. BBS2DAY has to be
started with a commandline parameter saying drive, path and filename of
your configurationfile.
e.g.: BBS2DAY c:\ra\BBS2DAY.LN1 <<- config file of line 1
BBS2DAY c:\ra\BBS2DAY.LN2 <<- config file of line 2
* Difference between BBS2DAY and B2DAY-UP:
BBS2DAY updates all the data files, (mailer and bbs) and generates a report.
B2DAY-UP ONLY updates the data of the BBS-system! (no mailer-data update
or report generation is possible with this tool).
═════════════════════════════════════════════════════════════════════════════
░▒▓█ INSTALLATION & CONFIGURATION For Opus, Maximus █▓▒░
═════════════════════════════════════════════════════════════════════════════
* Put BBS2DAY.EXE somewhere on your hard disk.
* Enter your info and wishes in the control file BBS2DAY.CTL. You won't
have much trouble with this. Make sure that BBS2DAY can find that file
in the current directory when it is started or place the path and
filename of your controlfile as a command-parameter after BBS2DAY.EXE.
* Put BBS2DAY in your batch file to run it in your daily event or after
each user. BBS2DAY generates a file called BBS2DAY.OPS (or BBS2DAY.MAX
if you're using Maximus), all activity of OPUS/Maximus will be stored
in this file (at this time these data will be taken out of a Binkley
compatible logfile).
* You can display these files to your users by using its typical
OPUS command "<CTRL-O>S2DAY".
* Registered users can also show their bbs-users a system usage graph
of the FrontDoor/Binkley/D'Bridge activity. To do so you just have
to place a additional line in your file saying: <CTRL-O>S2DAYMAIL
* BBS2DAY will create the reports in your text files path (which is obtained
from the CONFIG file). BBS2DAY will put a Ctrl-L (Screen Clearing Codes) in
the beginning of the file.
* BBS2DAY will create two files named 2DAY.BBS and 2DAY.GBS. A file
called BBS2DAY.DAT will be created by enabling, Mailer activity. This
file stores all information needed to process a mailer activity chart.
* It must be started everytime a user log's on (or off) so the system-
usage-graph will be up too date. You may also run BBS2DAY in a event if
you like, but then the system-usage-graph will not be so up too date as
running BBS2DAY everytime a user logs on (or off). Watch out, running
BBS2DAY when a user logs ON will cause him/her to wait a while.
* I suggest running BBS2DAY after a user logs off and everytime a mailer
called if FrontDoor/Binkley/D'Bridge activity is enabled.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ Command Line Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
BBS2DAY is typically run from a batch file. The only command line
option is the name of the control file if it's different from default
(BBS2DAY.CTL).
[<drive>:<path>][<FileName>.<Ext>]
Instructs BBS2DAY to use [<drive>:<path>][<FileName>.<Ext>] instead of
the standard BBS2DAY.CTL file.
e.g. BBS2DAY D:\CONFIGS\B2D_1.CTL
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - General Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
BBS2DAY uses a control file called BBS2DAY.CTL. This file contains
information pertaining to the environment in which BBS2DAY is to run.
It must be in the current directory unless specified on the command line.
Each line in the BBS2DAY.CTL file is limited to 255 characters. Any
characters that follow a semi-colon (;) or percent (%) are considered
comments and are ignored. The Control file provided on the BBS2DAY archive
can be edited or a new Control file may be created using any ASCII editor.
If you do not have any other editor you can use the DOS EDLIN editor (See
your DOS manual for more information). Any command line option may be
included in the control file. The settings in the control file will
override any setting defined in QuickBBS / RA / SuperBBS Control file.
Executing BBS2DAY in a multi-line environment is possible by creating
different control files for each line your running.
BBSSYSTEM <system>
The BBSsystem command tells BBS2DAY that it is operating in a
Remote Access (R), QuickBBS (Q), SuperBBS (S), OPUS (O) or
Maximus (M) environment.
Default: QuickBBS
RA <number>
The RA command tells BBS2DAY that Remote Access 1.10 or above
is used with the new LASTCALLER.BBS structure.
Default: 1.00
BBSLINE <byte>
The BBSline command tells BBS2DAY that the control file belongs
to line <byte> of Remote Access. You need this when running in
Multi-line mode.
Default: 1
BBSPATH [<Drive>:]<Path>
The BBSPATH specifies where your BBS software is located.
This is also the directory where BBS2DAY files will be stored.
An example would look like: BBSPATH C:\QuickBBS\
Default: (none) = current path
TEXTPATH <path>
This is the path where BBS2DAY will place all ASCII/ANSI text files.
You'll need this command if you don't want BBS2DAY to store this data
in the path defined in you Quickbbs / RA / SuperBBS control file.
If no BBS-configurationfile is found and no TEXTPATH added to
BBS2DAY.CTL the execution of this programm is aborted.
BBSSYSPATH <path>
BBSSysPath is the path that points to the directory in which your
BBS places the SYSINFO.BBS and LASTCALL.BBS files. This is where
BBS2DAY will get the name of your last user when running in
"DEFINABLE USAGE GRAPH" mode.
Default: BBSPATH (QuickBBS, SuperBBS) or
RA's System-path (defined in Config.RA)
BBSBASEPATH <path>
BBSBasePath is the path that points to the directory in which your
BBS places the USERS.BBS file. This is where BBS2DAY will find
startdate and time of the last bbs-user when running in
"DEFINABLE USAGE GRAPH" mode.
Default: BBSPATH (QuickBBS, SuperBBS) or
RA's Messagebase-path (defined in Config.RA)
AVATAR
This will create ???????.AVT files as well as the .ASC/.ANS files if
enabled * provided * that BBS2DAY is being used in a RA environment.
( BBSSYSTEM is set to (R)emoteAccess ).
DATEFORMAT <text>
This defines how BBS2DAY has to write dates. The <text> must
be composed of a number of special letters and (optionally) the
separators and spaces between the various parts of actual date.
In fact <text> should be a picture mask. BBS2DAY will recognize
these letters in your <text>:
DD or DDD for the day,
MM or MMM for the month,
YY or YYYY for the year.
So '90' for the year 1990 is defined with YY and the full year is will
be displayed by using YYYY.
max. length = 25 characters
Default: MMM DD, YYYY
e.g.: MMM DD, YYYY ---> Nov 12, 1990
MM/DD/YY ---> 10/09/90
DDD DD MMM YYYY ---> Mon 12 Nov 1990
in the YY's ---> in the 90's
As you can see, lots to experiment with.
Note: The text of DDD and MMM can be defined, just register!
CR/LF <digit>
defines the amount of CR/LineFeed's at the end of each report.
range: 0 to 9 cr/lf, displaying these files with RA/QBBS type 6
(Selection Menu / Display a text file and use as a menu) needs
at least 1 cr/lf, RA/QBBS type 5, 45 won't need one.
Default: 0
FILENAME <text>
defines the first 4 letters of the filenames used by BBS2DAY.
The default will be 2DAY, the 4 following letters can be defined
with FILENAMETYPE. This command is usefull in a multiline environment
if you want to display all files for each line on all BBS-lines.
FILENAMETYPE <digit>
defines the filenames used by BBS2DAY:
Report Type 0 Type 1 Type 2
-----------------------------------------------------
BBS : 2DAY.A?? 2DAY_B.A?? 2DAY_1.A??
Mailer-only : 2DAYMAIL.A?? 2DAY_M.A?? 2DAY_2.A??
BBS-Usage : 2DAYUSA.A?? 2DAY_U.A?? 2DAY_3.A??
BBS-Weekly : 2DAYWEEK.A?? 2DAY_W.A?? 2DAY_4.A??
BBS-Monthly : 2DAY4WKS.A?? 2DAY_4.A?? 2DAY_5.A??
BBS-Dayly : 2DAY24HR.A?? 2DAY_H.A?? 2DAY_6.A??
Note: 2DAY can be re-defined by FILENAME <text>
Default: Type 0
HEADER <text ^? text>
define your own header in you native language or just change the text
of the default in case you don't like mine. This text shouldn't have
ansi-characters in it because it's displayed in the ascii-report too.
max. length: 79 characters
The "^?" stands for control-codes, currently supported ones are :-
^F == will represent the number of days the activity started
^KB == date the activity started at.
^KE == date of chart-creation.
Default: "Average Percentage of System Usage by Hour
for the Last ^F Days"
AVG <text>
define average text
max. length: 4 characters, no ansi-codes
Default: "AVG "
DEFINE <text>
enable definition text, this text explains the characters used in
these reports, max. length: 70 characters
Default: "M,m = Mailer C,c = Human Caller"
Note: using ansi-codes will BBS2DAY center-option to malfunction.
you have to correct this by your own with "<ESC>#C"
This text will be displayed in ascii-reports too!
IBM-DEFINE <text>
enable definition text for the IBM-characterset.
this text explains the characters used in these reports.
max. length: 70 characters
Default: "║,╥ = Mailer █,▄ = Human Caller"
Note: using ansi-codes will cause BBS2DAY center-option to malfunction.
You will have to correct this on your own with a "<ESC>#C".
This text will be displayed in ascii-reports too!
IBM-ASCII
this command enables IBM-ASCII codes in the ASCII report.
This means that not only standard ascii characters but also the
IBM-characters ASCII 128 & higher) are used to create
all ascii-reports
IBM-ANSI
this command enables IBM-ASCII codes in the ANSI report.
This means that not only standard ascii characters but also
the IBM-characters ASCII 128 & higher) are used in the creation of
all ansi-reports
Hint: enable IBM-ANSI, use ansi-codes in IBM-DEFINE <text>
disable IBM-ASCII, don't place ansi-codes into DEFINE <text>
Now you'll get a report in ansi-codes with IBM-characters
including ansi-codes in you chart explaination and a plain ascii
file (ext: ASC). This work also with all other output-files
of BBS2DAY.
COLORS
Colours will be defined by numbers and are calculated like this:
Number = foregroundcolour + backgroundcolour * 16
Dark Colours ║
(Foreground & ║ Light Colours
Background) ║ (Foreground)
═══════════╤═══╬══════════════╤════
Black │ 0 ║ DarkGray │ 8
Blue │ 1 ║ LightBlue │ 9
Green │ 2 ║ LightGreen │ 10
Cyan │ 3 ║ LightCyan │ 11
Red │ 4 ║ LightRed │ 12
Magenta │ 5 ║ LightMagenta │ 13
Brown │ 6 ║ Yellow │ 14
LightGray │ 7 ║ White │ 15
For flashing (blinking) text foreground, add 128 to number.
e.g. if you want a yellow flashing text on green background
the colour-number would be 128 + 15 + (2 * 16) = 175
COLOR-HIGH <number>
title color of ansi-chart
Default: "14" (yellow)
COLOR-NORM <number>
border color of ansi-chart
Default: "7" (grey)
COLOR-MAILER <number>
chart colors for mailer ansi-chart
Default: "7" (grey)
COLOR-CALLER <number>
chart colors for human caller ansi-chart
Default: "15" (white)
Note: It's a good idea to have the same background colors
for mailer and human caller.
WAIT-FOR-KEY
enables the output of "Press Enter to continue:" and let's the user
press <Enter> when he/she's ready.
PRESSENTER <text>
define the text to display when pausing
max. length: 65 characters
Default: "Press [Enter] to continue:"
COLOR-PRESSCOLOR <number>
chart colors for "Press .."
max. length: 3 characters
Default: "13" (lightmagenta)
PRESSCTRLA <text>
define the key to let user "press Enter",
max. length: 10 characters
Default: "<CTRL-A>"
ABORT output of report
ABORT ON
enables the output of the STOPON character
which normaly allows the user to stop output
by pressing <S>
ABORT OFF
enables the output of the STOPOFF character
which normaly disallows the user to stop output
by pressing <S>.
STOPON <text>
defines the characters for TURN <S>TOP ABORTING ON
max. length: 10 characters
Default: "<CTRL-C>"
STOPOFF <text>
define characters for TURN <S>TOP ABORTING OFF
max. length: 10 characters
Default: "<CTRL-B>"
NOMORE
enables Page/More Prompt function
With this option enabled NO prompts like "More ?" will occur.
MOREON <text>
define characters for TURN MORE PROMPTS ON
max. length: 10 characters
Default: "<CTRL-E>"
MOREOFF <text>
define characters for TURN MORE PROMPTS OFF
max. length: 10 characters
Default: "<CTRL-E>"
LOGLEVEL <byte>
When executing BBS2DAY will write a log in the current directory. The
loglevel option allows the sysop to set the level of log reporting.
Each level will include the information from lower log levels as well
as the current level. The valid levels are from 0 to 5 with the
default being 0. The log level settings correspond to the following:
Level Log Entries
----- -----------
0 No log file (Default)
1 Dos Errors
2 Warnings, missing files
3 User - Online-date & time information
4 Information
5 Detailed processing information
An example of this command is LOGLEVEL 3. This log level would
produce a log that contained only references to DOS errors, warnings,
and brief online-time information.
DEBUG
in Debug-Mode you'll get a lot of information about what's
going on displayed on your screen. BBS2DAY slows down a little
bit down due to the ammount of vscreen-output but it's a nice option
to see you have configured everything the way you require or to solve
some strange problems.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - Mailer Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
There now follows 4 seperate sections which detail the configurations for
the control file depending on which front end mailer you have. Shown below
are the general options which is used by all the available mailer type
options
MAIL
This command invokes the Mailer mode which causes all the Mailer
activity to be included in the charts.
MAILERSYSTEM <system>
The MailerSystem command tells BBS2DAY that it is operating in a
FrontDoor (F), Binkley (B) or D'Bridge (D) environment.
Default: FrontDoor
MAILLOG <filename>
The next control file line is the MailLog statement. This is
the directory and filename of your mailers logfile.
This control statement is required in Mailer mode and should be
of the form: MAILLOG [<Drive>:<Path>]<filename>.<ext>
Note: This command has a different meaning when used with the
D'Bridge mailer. ( Refer to the section on the D'Bridge
set up for further guidance ).
MAILHEADER <text ^? text>
define your own header in you native language or just change the text
of the default is case you don't like mine. This text shouldn't have
ansi-characters in it because it's displayed in the ascii-report too.
max. length: 79 characters
"^?" stands for control-codes, allowed are :
^F == will represent the number of days the activity started
^KB == date the activity started at.
^KE == date of chart-creation.
Default: "Average Percentage of Mailer Usage by Hour for the
Last ^F Days"
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - FrontDoor Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
If you're including FrontDoor activity please have the following
four lines:
" * Sent/Rcvd files "
" ~ Session information "
" - Trivial messages "
" + Brief messages "
set to Y E S in FrontDoor-Setup Mailer / Miscellaneous / Log.
HINT: It's a good idea to set all log options to YES!
With FrontDoor 2.0 you have to do the following if you want a faster
recognition . The setup for FD 1.99c can be used, but if you are
using FD 2.0, then these extra commands can be employed.
a. Set " $ Cost Information " to YES in FrontDoor-Setup Mailer /
Miscellaneous / Log.
b. Place this command into your configuration file to speed up
the processing :-
FRONTDOOR 2.0
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - BinkleyTerm Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
BBS2DAY when used with BinkleyTerm reads all lines starting with # and *.
The exact online-time is calculated from these lines in your log-file:
# dd mmm hh:mm:ss BINK Connect ..... / start of any session
AND one of these two lines:
* dd mmm hh:mm:ss BINK Remote uses ..... / start of mailer-session
* dd mmm hh:mm:ss BINK Sending mail ..... / start of mailer-session
one of these two lines:
* dd mmm hh:mm:ss BINK Lost Carrier / end of session
OR
* dd mmm hh:mm:ss BINK End of ...... / end of session
* dd mmm hh:mm:ss BINK End of ... session / end of session
BBS2DAY checks for both "startline", so they have to be defined in
it's way of appearrence! Time is calculated from occurrance of the
first "startline" to the first apperance of one the two "endlines".
You can change these lines by inserting the following code into the
configuration file:
BINK-START char <- Default-char: #
BINK-STARTTEXT text <- Default-text: BINK Connect
BINK-START2 char <- Default-char: *
BINK-STARTTEXT2 text <- Default-text: BINK Remote Uses
BINK-START3 char <- Default-char: *
BINK-STARTTEXT3 text <- Default-text: BINK Sending Mail
BINK-END char <- Default-char: *
BINK-ENDTEXT text <- Default-text see next line
or BINK-ENDTEXT text @ text <- Default-text: BINK End of @ Session
BINK-END2 char <- Default-char: *
BINK-ENDTEXT2 text <- Default-text: BINK Lost Carrier
or BINK-ENDTEXT2 text @ text <- Default-text see previous line
Note: @ seperates two strings to search for in just one line.
If you know how a lines starts and ends, you can place a '@'
between them and BBS2DAY tries to recognize them.
@ stands for a undefined amount of characters.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - D'Bridge Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
┌──────────────────────────────┐
│ D'Bridge versions below 1.30 │
└──────────────────────────────┘
You can change these lines by inserting the following code into the
configuration file:
Place the following lines into your configuration file:
DB-STARTTEXT text <- Default-text: EMSI:
DB-STARTTEXT2 text <- Default-text: YOOHOO:
DB-ENDTEXT text <- Recommended: PACKET
DB-ENDTEXT2 text <- Recommended: SUCCESSFUL
DB-ENDTEXT3 text <- Recommended: BAD/INCOMPLETE ARCHIVE
┌───────────────────────┐
│ D'Bridge version 1.30 │
└───────────────────────┘
When used with D'Bridge version 1.30, the only option(s) that BBS2DAY
requires to know is where the D'Bridge system directory is. This
is defined by the option MAILLOG as shown below. The other option
is the enablement of the option DB-LOGOPTION.
MAILLOG <path>
This is the directory without any filename of your D'Bridge
system directory. This should be the same as the enviroment
variable you have set for D'Bridge, ie. Set DB=C:\DB
DB-LOGOPTION <char>
This control statement is required in Mailer mode w/ DB
enabled and should be of this form: DB-LOGOPTION <char>
<char> may be N for none, T for Terse or V for Verbose.
┌──────────────────────────────┐
│ D'Bridge versions above 1.30 │
└──────────────────────────────┘
DB-LOGOPTION NONE
This control statement is required in Mailer mode w/ DB
enabled and should be set to NONE. This let's BBS2DAY
read the DBRIDGE.DL? files located in MAILLOG <path> (see v1.30).
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - OPUS Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
OPUS-COMMAND <text>
enable execution of an OPUS-command at end of BBS/GBS files.
OPUS-WAIT <text>
define text to show to users before executing an OPUS-COMMAND.
This string will be displayed as it is.
max. length: 80 characters
Default: <none>
OPUS-ANSI-EXT <text>
define the extension of OPUS ANSI-file (e.g. OEC)
Setting this variable to 'OEC' will cause BBS2DAY to create only one
file with ansi-codes in it, it's up to you to change these ansi-
commands into OEC-commands.
max. Length: 3 characters
Default: GBS
OPUS-LOGPATH <filename>
drive, path and filename of OPUS logfile. You will have to use this
command due to the fact BBS2Day is not reading any PRM-file of
OPUS 1.1x
BBS2DAY reads all lines starting with (blank) and + (plus).
The exact online-time is calculated from these lines in your log-file:
dd mmm hh:mm:ss OPUS Connect ..... / start of any session
+ dd mmm hh:mm:ss OPUS ... Off-line. Calls ..... / start of mailer-session
You can change these lines by inserting the following code into the
configuration file:
OPUS-START char <- Default-char: (blank)
OPUS-STARTTEXT text <- Default-text: OPUS Connect
OPUS-END char <- Default-char: +
OPUS-ENDTEXT text <- Default-text see next line
or OPUS-ENDTEXT text @ text <- Default-text: OPUS @ Off-line. Calls
Note: @ seperates two strings to search for in just one line.
If you know how a lines starts and ends, you can place a '@'
between them and BBS2DAY tries to recognize them.
@ stands for a undefined amount of characters.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ The Control File (BBS2DAY.CTL) - MAXIMUS Options █▓▒░
═════════════════════════════════════════════════════════════════════════════
OPUS-COMMAND <text>
enable execution of OPUS/Maximus-command at end of BBS/GBS files.
OPUS-WAIT <text>
define text to show to users before executing an OPUS/Maximus-COMMAND.
This string will be displayed as it is.
max. length: 80 characters
Default: <none>
OPUS-ANSI-EXT <text>
define the extension of an OPUS/Maximus ANSI-file (e.g. OEC). Setting
this variable to 'OEC' will cause BBS2DAY to create only one file with
ansi-codes in it, it's up to you to change these ansi-commands into
OEC-commands.
max. Length: 3 characters
Default: GBS
MAXS-LOGPATH <filename>
drive, path and filename of Maximus logfile
BBS2DAY reads all lines starting with (blank) and + (plus).
The exact online-time is calculated from these lines in your log-file:
dd mmm hh:mm:ss MAX ... Calling ..... / start of session
+ dd mmm hh:mm:ss MAX ... Off-line. Calls ..... / end of session
You can change these lines by inserting the following code into the
configuration file:
MAXS-START char <- Default-char: +
MAXS-STARTTEXT text <- Default-text see next line
or MAXS-STARTTEXT text @ text <- Default-text: MAX @ Calling
MAXS-END char <- Default-char: +
MAXS-ENDTEXT text <- Default-text see next line
or MAXS-ENDTEXT text @ text <- Default-text: MAX @ Off-line. Calls
Note: @ seperates two strings to search for in just one line.
If you know how a lines starts and ends, you can place a '@'
between them and BBS2DAY tries to recognize them.
@ stands for a undefined amount of characters.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ B2DAY-UP, BBS2DAY "DEFINABLE-USAGE" Configuration █▓▒░
═════════════════════════════════════════════════════════════════════════════
B2DAY-UP.EXE is used to update bbs-system usage data in a very fast way.
No reports will be generated with this program. Please run this program
after a user logs off instead of BBS2DAY if you don't want to create a
report after each user's logoff.
B2DAYCLR.EXE is used for maintenance only, you can clean the datafile of
unwanted dates. Depending on your diskspace you should run this program
more or less as required. (20kb is needed for a years worth of BBS
data and a further 20Kb for mailer data ).
Special commands:-
¡EMPTY!
If you want to set a string-recognition text or path / filename to an
empty textstring just enter the command with ¡EMPTY! behind it
(seperated by a blank).
¡BLANK! or ¡
If you want to set a stringtext or a charater-command to blank enter
the command followed by< a blank and ¡BLANK!. Defining charcters to
blank would do fine with just the ¡ (ASCII-173).
Note: ¡ can be produced by pressing ALT and entering 173.
(It's IBM-PC's extended ASCII-code 173).
DEFINABLE-USAGE
this command will enable BBS2DAY to generate you defineable usage graph.
Default: def.usage disabled
USAGELENGTH <byte>
will generate a report of the last <byte> days.
BBS2DAY generates files called :-
2DAYUSA.ASC/ANS (filename type 0)
2DAY_U.ASC/ANS (filename type 1)
2DAY_3.ASC/ANS (filename type 2)
Default: 14
USAGEHEADER <text ^? text>
define your own header in your native language or just change the text
of the default in case you don't like mine. This text shouldn't have
ansi-characters in it because it's displayed in the ascii-report too.
max. length: 79 characters
"^?" stands for control-codes, allowed are :
^F == will represent the number of days the activity started
Default: "Average Percentage of System Usage by Hour
for the Last ^F Days"
USAGECOMPRESS <byte>
will compress the existing data to the last <byte> days.
This is used by B2DAYCLR.EXE only. The minimum value is 28.
USAGEWEEK
This will generate a report of the whole week (sunday to saturday).
The neccessary data will be saved in BBS2DAY.DTA.
BBS2DAY generates files called :-
2DAYWEEK.ASC/ANS (filenametype 0)
2DAY_W.ASC/ANS (filenametype 1)
2DAY_4.ASC/ANS (filenametype 2)
WEEKCHART <char>
This will change the resolution of the weekly-chart.
It's calculated on a basis of minutes per day (M) or on minutes per
week (D). The chart with minutes per week will be seven times higher
than minutes per week. This is due to the seven days of a week and
the chart will report the middle average on every day instead of the
summary of the whole week.
Default: M
WEEKHEADER <text ^? text>
Enables you to define your own header in your native language or just
change the text of the default header in case you don't like mine.
This text shouldn't have ansi-characters in it because it's displayed
in the ascii-report too.
max. length: 79 characters
"^?" stands for control-codes, allowed are :
^F == will represent the number of days the activity started
Default: "Average Percentage of System Usage by Day
for the Last ^F Weeks"
USAGEMONTH
This will generate a report of the last four weeks (1 to 28 days).
The neccessary data will be taken from the datfiles BBS2DAY generates.
BBS2DAY generates files called :-
2DAY4WKS.A?? (filenametype 0)
2DAY_4.A?? (filenametype 1)
2DAY_5.A?? (filenametype 2)
MONTHHEADER <text>
Enables you to define your own header in your native language or just
change the text of the default header in case you don't like mine.
This text shouldn't have ansi-characters in it because it's displayed
in the ascii-report too.
max. length: 79 characters
Default: "Average Percentage of System Usage by Day
for the Last 28 Days"
24HOURS
Enables BBS2DAY to create a 24 hours chart of mailer and BBS.
A valid chart can be made by executing B2D24HRS.EXE, this
program updates all data and builts the wanted chart. Updates
can be made with B2DAY-UP, too but only B2D24HRS and BSB2DAY
create these chart. I suggest running B2D24HRS instead of
B2DAY-UP.EXE every time a user logs off and BBS2DAY.EXE to update
this chart with mailer-data. The neccessary data will be taken
from the datafiles BBS2DAY and/or B2D24HRS generate (BBS2DAY%.D??).
BBS2DAY generates files called :-
2DAY24HR.A?? (filenametype 0)
2DAY_6.A?? (filenametype 1)
2DAY_H.A?? (filenametype 2)
It's a good idea to run BBS2DAY each time a mailer called, so the
mailer part of this report will be up-to-date, too.
24HOURSHEADER <text>
Enables you to define your own header in your native language or just
change the text of the default header in case you don't like mine.
This text shouldn't have ansi-characters in it because it's displayed
in the ascii-report too.
max. length: 79 characters
Default: "Average Percentage of System Usage by Hour
for the Last 28 Hours"
24HOURS:LOG
Enables you to get a logfile "B2D24HRS.LOG" with all 24hours
depending data in it. You can use this file to check the
generated report in case of strange behaviours.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ Registered Version Additional Configuration █▓▒░
═════════════════════════════════════════════════════════════════════════════
MAILCHART
create extra report for Mailer Activity these files will be called :-
2DAYMAIL.ANS/ASC ( filename type 0 )
2DAY_M.ANS/ASC ( filename type 1 )
2DAY_2.ANS/ASC ( filename type 2 )
MAILCHAR
let's BBS2DAY use callers-characters in 2DAYMAIL ansi file.
Define other IBM-characters in all reports:
IBM-CharCLo <char> Default: "▄" Define caller half size,
IBM-CharCHi <char> Default: "█" Define caller full size
IBM-CharCALo <char> Default: "▄" Define caller half size middle avg.
IBM-CharCAHi <char> Default: "█" Define caller full size middle avg.
IBM-CharMLo <char> Default: "╥" Define mailer half size
IBM-CharMHi <char> Default: "║" Define mailer full size
IBM-CharMALo <char> Default: "╥" Define mailer half size middle avg.
IBM-CharMAHi <char> Default: "╫" Define mailer full size middle avg.
IBM-CharAVG <char> Default: "»" Define middle average sign
IBM-CharMDL <char> Default: "─" Define middle average (line)
Define other Standard-ASCII-characters in all reports:
ASC-CharCLo <char> Default: "c" Define caller half size
ASC-CharCHi <char> Default: "C" Define caller full size
ASC-CharMLo <char> Default: "m" Define Mailer half size
ASC-CharMHi <char> Default: "M" Define mailer full size
ASC-CharAVG <char> Default: ">" Define middle average sign
ASC-CharMDL <char> Default: "-" Define middle average (line)
NAME-DAY:<DAY> <text>
<DAY> is SUN, MON, TUE, WED, THU, FRI or SAT
Define name of day, max 3 characters.
Defaults: NAME-DAY:SUN Sun
NAME-DAY:MON Mon
NAME-DAY:TUE Tue
NAME-DAY:WED Wed
NAME-DAY:THU Thu
NAME-DAY:FRI Fri
NAME-DAY:SAT Sat
e.g.: NAME-DAY:MON Mo --> DDD on monday will be displayed as Mo
NAME-DAY:<MONTH> <text>
<MONTH> is JAN, FEB, MAR, APR, MAY, JUN,
JUL, AUG, SEP, OCT, NOV or DEC
Define name of month, max 10 characters.
Defaults: NAME-MONTH:JAN Jan
NAME-MONTH:FEB Feb
NAME-MONTH:MAR Mar
NAME-MONTH:APR Apr
NAME-MONTH:MAY May
NAME-MONTH:JUN Jun
NAME-MONTH:JUL Jul
NAME-MONTH:AUG Aug
NAME-MONTH:SEP Sep
NAME-MONTH:OCT Oct
NAME-MONTH:NOV Nov
NAME-MONTH:DEC Dec
e.g.: NAME-MONTH:NOV November
--> MMM in november will be displayed as November
═════════════════════════════════════════════════════════════════════════════
░▒▓█ VERSION HISTORY █▓▒░
═════════════════════════════════════════════════════════════════════════════
v1.00 QuickBBS chart generated as a copy of QBS
v2.00 QuickBBS,RA and FrontDoor are supported, seperate chart for
registered user implemented.
v2.10 BINKLEY is supported. Changes all Mailernames from FD to MAIL
OPUS is supported (beta-test). QuickBBS / RA configurationfile
can be ignored by adding TEXTPATH to controlfile.
bug in day-lap fixed, no more 1440 minutes if mailer logged in
at 23.00hrs and leaves at 0.00hrs.
v2.11ß
2.12ß
2.13ß Bug in daycount fixed, so Timelog.BBS may be older than a year.
implemented D'Bridge v1.18/v1.30 mailer-activity.
appended ANSI-reset-command to end of chart. (ESC [0m)
v2.20 Update to D'Bridge v1.31, 2 START and 3 END commands
are recognized. BBS2DAY tested with LZEXE and NO problems
were found.
v2.30 Cosmetic changes, definable configuration-filename which can be
assigned on the commandline. Higher resolution in graphics.
Name modification (QBBS2DAY -> BBS2DAY). SuperBBS support.
Added dates (^KB and ^KE) to definable header. Added logfile.
Full BINKLEY 2.40 - Mailer recognition. fixed middle average-line
bug.
v2.31 Pause and Page/More commands added for your convenience.
v2.99ß New utilities: BBSUA BBSUSA! and BBSUSAM released
definable reports with maintenance unit.
v3.00 Fixed some bugs in BBS2DAY. BBSUSA is moved into BBS2DAY, so
no running of two different programms doing the same stuff.
B2DAY-Up updates all BBS2DAY depending files for BBS usage.
B2DAYclr can be used as maintenance utility.
v3.01 Fixed mailerdepending bug in BBS2DAY. Bug in creating chart
with mailer and BBS eliminated, the chart will no longer be
destroyed by wrong characters.
v3.10 DATEFORMAT now more definable to registered users. Weekly BBS
chart now available (no beta-test). CR/LF at End Of File now
definable. Bug in log-file recognition removed (wrong logdate
on calls between day-switch (pm to am)). Changed recognition-text
to D'Bridge 1.31. Added a samples of mailer-charts.
Added filename-parameter to define own names in conjuction with
RA/QBBS type 6 command. OPUS 1.1x is supported. BBS2DAY has been
run, compressed by PKLITE 1.03 without any problems, so feel free
to use PKLITE or LZEXE. Fixed bug, which messed up usage-chart,
due to problems in date-recognition on the first <usagelength>
days after new years day.
v3.11ß
3.12ß Support of Maximus added.
Rewrote code for Logfile-recognition (bug-fix). In OPUS/Maximus
"OEC"-mode (enabled with "OPUS_ANSI_EXT OEC") will no *.BBS file
be produced. Better support of the D'Bridge mailer.
Support of Remote Access 1.00 Avatar mode (ASC/ANS/AVT files).
3.20 Fixed bug doubling data in usage- and mailer-datafiles. Filenames
can now be defined by user. A 24-hours-chart can be created.
RA 1.10 support.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ THE FUTURE █▓▒░
═════════════════════════════════════════════════════════════════════════════
Until now I spent hours thinking, writing, converting, debugging and
documenting BBS2DAY, and I will keep on doing that. BBS2DAY is a little
bit crippled: if you don't register,
* it will not create an extra file showing FrontDoor/Binkley/D'Bridge's
Mailer-activity (2DAYMAIL.ASC/ANS).
* you can't define the day and month names in your chart nor change any
characters of the chart.
If you use this program for a period of time (30 days) and you decide
you like it, you can get a registration key by sending the EXACT TEXT you
want BBS2DAY registered too (Bulletin Board name) and which version you
are currently using, along with any questions, comments, suggestions and
bug-reports, and of course your (net) mail address, to:
Robert Hermans
Hoosveld 35
NL - 6075 DC Herkenbosch
The Netherlands
If you run into any bugs or problems you cannot solve, I can be reached
either through my BBS or my postal address as published above.
DC SKYline @fidoNet 2:512/38
INTL +31-4752-5306
V21, V22, V22b, V32, V32b, 9k6/14k4-HST, MNP5 & V42b
═════════════════════════════════════════════════════════════════════════════
░▒▓█ REGISTRATION █▓▒░
═════════════════════════════════════════════════════════════════════════════
There are two ways of registration :
1.) By using BBS2DAY on a regulary basis you MUST SEND a POSTCARD to my
home address (shown above). All I ask is to be able to show your
postcard to my grandchildren and say "Look at this one Becky - here's
another nice postcard from a guy at Lake Powell, Arizona". If you're
using this way you'll have to call my BBS to receive your key. Please
allow up to 21 days too process due to mail-transportation speed.
2.) A contribution of at least US$ 15.00, sent to the above address, would
be greatly appreciated. Dutch guildes or german marks will be accepted
as well. Because i really like this way you'll receive your key thru
Netmail (within a week after receiving your money). In case your node
number isn't present, you'll get your desired key by normal mail (don't
forget your exact address). (See also money registration's on the next
page).
═════════════════════════════════════════════════════════════════════════════
░▒▓█ MONEY REGISTRATION'S █▓▒░
═════════════════════════════════════════════════════════════════════════════
How to pay:
* By postal money order or by international money order. Personal
cheques (if they are not EuroCheques) will cost me extra money to
transfer, so add US$ 10.00 for transfer if you use such a cheque.
* By using an EuroCheque please do the following:
Calculate the amount of US-Dollars into dutch or german money and
write out the cheque in this currency (Hfl or DM). Please check out
the local transfer rates for US-Dollars to dutch or german money.
So just use german or dutch currency on the cheque and N E V E R
use US-Dollars or other currencies. Using US-Dollars o.o. will mean
an extra charge of around US $ 15.00 to transfer the cheque.
Write the Eurocheque out on: Robert Hermans, Herkenbosch
* Sending money directly, but please make sure you send it with some kind
of safety, so you can make sure yourself that I received the money. When
you send money, you can also send money in your own currency, but make sure
to use a valid exchange rate. This is the exchange rate on the day you
send the money to me.
* There is NO way I can accept credit-card transfers.
═════════════════════════════════════════════════════════════════════════════
░▒▓█ OFFICIAL BBS2DAY DISTRIBUTION SITES █▓▒░
═════════════════════════════════════════════════════════════════════════════
HOLLAND Sysop : Robert Hermans
BBS Name : DC SKYline
E-Mail Address : 2:512/38 @fidonet
Tel No : +31-4752-5306
Modem Speeds : V22bis, V32bis , HST , V42bis
GERMANY Sysop : Wim Abels
BBS Name : Blues Project
E-Mail Address : 2:242/20 @fidonet
Tel No : +49-211-5961291
Modem Speeds : V22bis, V32 , HST , V42bis
U.K. Sysop : Peter Burnett
BBS Name : Piston Popper's
E-Mail Address : 2:440/80 @fidonet
Tel No : +44-424-853361
Modem Speeds : V22bis, V32 , HST , V42bis
U.S.A. Sysop : John Friedrich
BBS Name : Freddy's Funland
E-Mail Address : 1:369/33 @fidonet
Tel No : +1-305-384-0970
Modem Speeds : V22bis, HST
You can always request the latest version here, using the magic
name "BBS2DAY". It's also released thru the SDS, the name will be
B2DAY???.* with ??? represending the version number times 100 (v3.10 = 310).
I would like to thank my beta testers / support nodes for their help with
this and many other projects. I couldn't have done it without them!